Skip to content

Fix: use public user_agent_entry connect parameter#64

Merged
jprakash-db merged 1 commit into
mainfrom
cursor/fix-user-agent-entry-rename
May 27, 2026
Merged

Fix: use public user_agent_entry connect parameter#64
jprakash-db merged 1 commit into
mainfrom
cursor/fix-user-agent-entry-rename

Conversation

@jprakash-db
Copy link
Copy Markdown
Collaborator

The databricks-sql-connector 4.0.1 release renamed the connect parameter _user_agent_entry to user_agent_entry and emits a deprecation warning when the old name is passed. Switch the dialect's do_connect listener and all call sites to the new name, pop any legacy _user_agent_entry callers still supply so it isn't forwarded, and bump the connector floor to >=4.0.1 to guarantee the new key is understood. Fixes #36.

The databricks-sql-connector 4.0.1 release renamed the connect
parameter `_user_agent_entry` to `user_agent_entry` and emits a
deprecation warning when the old name is passed. Switch the dialect's
`do_connect` listener and all call sites to the new name, pop any
legacy `_user_agent_entry` callers still supply so it isn't forwarded,
and bump the connector floor to >=4.0.1 to guarantee the new key is
understood. Fixes #36.
Copy link
Copy Markdown
Collaborator

@msrathore-db msrathore-db left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jprakash-db jprakash-db merged commit 7e74a3f into main May 27, 2026
8 of 9 checks passed
@gdubya
Copy link
Copy Markdown

gdubya commented May 27, 2026

Does this also resolve #45 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use 'user_agent_entry' instead of '_user_agent_entry' when connecting to Databricks SQL

3 participants